Context cancellation timing issue: The context is cancelled immediately after consuming the stream channel (line 284), but it should be deferred to ensure it's cancelled even if an error occurs during stream consumption. The current pattern doesn't follow Go best practices for context cancellation. Move the cancel() call to a defer statement immediately after line 264 to ensure proper cleanup. This is the pattern used elsewhere in the codebase (e.g., go/cli/internal/cli/agent/invoke.go:102-103).

The manual backoff calculation defaultRetry.Duration * time.Duration(1<<(attempt-1)) is a simple exponential backoff but doesn't use the Factor and Jitter fields from defaultRetry (lines 181-186). The defaultRetry config specifies Factor: 2.0 and Jitter: 0.2, but this implementation ignores both. Either use these fields in the calculation (backoff = Duration * Factor^(attempt-1) with jitter), or consider using wait.ExponentialBackoff or wait.ExponentialBackoffWithContext which properly implements the backoff strategy including jitter.

The per-attempt timeout has been reduced from 30 seconds (original shared timeout across all attempts) to 10 seconds per attempt. While this provides a clearer timeout boundary per attempt, verify that 10 seconds is sufficient for streaming operations in your test environment. If the streaming response legitimately takes longer than 10 seconds, this could cause flaky test failures.